chore(e2e): just recipes for the gh-automatable setup#49
Merged
Conversation
The gh-automatable part of e2e setup: `just e2e-setup <org> <app-slug> <pem>` discovers the App id + installation id from the org's installations and sets all four WARDEN_E2E_* repo secrets; `just e2e-run [apply]` dispatches the workflow. (Creating the App/org and downloading the .pem remain web-only.) README documents the flow. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Answers "how much of e2e setup can gh do?" by codifying the automatable part.
just e2e-setup <test-org> <app-slug> <pem-path>gh api /orgs/<org>/installations→ discovers the App id + installation id (no need to copy them by hand)gh secret set→ wires all fourWARDEN_E2E_*repo secrets (org, app-id, installation-id, private-key-from-pem)just e2e-run [apply]gh workflow run e2e.yml(Phase 1; passtruefor Phase 2), and prints the watch commandStill web-only (gh/API can't)
Creating the test org, creating the GitHub App, downloading its
.pem, and clicking Install — those are the manual prereqs. Everything after is one command.README updated with the flow.
🤖 Generated with Claude Code